Smart harbor device for intelligent updating and selection for use of transaction processing terminal devices

ABSTRACT

There are provided systems and methods for a smart harbor device for intelligent updating and selection for use of transaction processing terminal devices. A smart harbor device may be used to provide updating, servicing, and other maintenance of transaction processing terminal devices, such as EMV terminals used in retail transaction processing. The smart harbor device may include a port where the transaction processing terminal devices may be places, and the smart harbor device may connect to each of the transaction processing terminal devices. Once connected, the smart harbor device may run diagnostics to determine the statuses and conditions for each of the transaction processing terminal devices and maintenance the transaction processing terminal devices. The maintenance may be performed at times where the transaction processing terminal devices are not required for use. Additionally, the smart harbor device may intelligently select one based on statuses and device capabilities.

TECHNICAL FIELD

The present application generally relates to transaction processingterminals, and more specifically to a smart harbor device forintelligent updating and selection for use of transaction processingterminal devices.

BACKGROUND

With the increasing use of payment cards, such as debit and credit cardshaving a magnetic stripe or embedded chip with stored data, merchantshave increased use of mobile payment processing terminals acting as thepoint-of-sale device. For example, mobile magnetic stripe and/or EMVcard readers are capable of providing mobile payment processing at amerchant location or with a mobile merchant through a small devicecapable of being carried by the merchant or merchant's employees. Thesepayment terminal devices often include a reader type component, as wellas necessary hardware that may read payment data encoded on the cardsmemory (e.g., the magnetic stripe and/or EMV chip), as well as acommunication component that may communicate the payment data to acomputing device for payment processing. Thus, the payment terminaldevices often connect to another computing device, such as mobilecommunication devices of the merchant or merchant's employees, where themobile communication devices may have sales and payment processingapplications to effectuate a sale and a payment from a customer to themerchant. However, these mobile payment terminal devices may requiremaintenance, which may interfere with usage of the mobile paymentterminal devices, particularly where the merchant or merchant's employeemay connect to a device and realize the device requires servicing.Moreover, with the variability in types of mobile communication devices,available hardware, and operating systems, certain mobile paymentterminal devices having particular features and/or operability may bebetter suited for certain mobile communication devices, which may not beimmediately apparent to the merchant or merchant's employee.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a networked system suitable forimplementing the processes described herein, according to an embodiment;

FIG. 2A is an exemplary smart harbor device for intelligent updating andselection for use of transaction processing terminal devices, accordingto an embodiment;

FIG. 2B is an exemplary environment displaying use of a transactionprocessing terminal device synchronized from a smart harbor device,according to an embodiment;

FIG. 2C is an exemplary environment displaying updating of transactionprocessing terminal devices using a smart harbor device, according to anembodiment;

FIG. 2D is an exemplary environment displaying selection of atransaction processing terminal device for connection to a mobilecommunication device by a smart harbor device, according to anembodiment;

FIG. 3 is an exemplary system environment having interacting devices foruse of a smart harbor device for intelligent updating and selection foruse of transaction processing terminal devices, according to anembodiment;

FIG. 4 is an exemplary process flowchart for use of a smart harbordevice for intelligent updating and selection for use of transactionprocessing terminal devices, according to an embodiment; and

FIG. 5 is a block diagram of a computer system suitable for implementingone or more components in FIG. 1, according to an embodiment.

Embodiments of the present disclosure and their advantages are bestunderstood by referring to the detailed description that follows. Itshould be appreciated that like reference numerals are used to identifylike elements illustrated in one or more of the figures, whereinshowings therein are for purposes of illustrating embodiments of thepresent disclosure and not for purposes of limiting the same.

DETAILED DESCRIPTION

Provided are methods utilized for a smart harbor device for intelligentupdating and selection for use of transaction processing terminaldevices. Systems suitable for practicing methods of the presentdisclosure are also provided.

A communication device may be utilized by a user, such as a merchant ormerchant employee, to perform various merchant and transactionprocesses, including sales, checkout, payment processing, and othermerchant transactions. In this regard, the communication device, such asa mobile smart phone, tablet computer, wearable computing device, orother type of computing device, may function as a mobile transactionprocessing device to provide sales to customers and process transactionswith the merchant. The communication device may further be utilized toperform other merchant tasks, which may include communicating withcustomers, accessing and navigating within a merchant website, and/orother services associated with the merchant. The communication devicemay therefore include one or more software processes to perform theaforementioned actions, which may be included with one or moreapplications executing on the communication device. For example, thecommunication device may include a sales application, which may providesales, checkout, and payment processing services to the user. Suchsoftware processes may be utilized through the hardware features of thecommunication device, such as the hardware processor, device display andother output devices, network access components, input devices, etc. Thecommunication device may therefore include various hardware and softwarefeatures. Additionally, the communication device may include additionalhardware features that allow execution of the processes, such as a powersource (e.g., a battery, power cord for an outlet, etc.).

In order to accept input of payment information from a customer, thecommunication device may interface with a mobile transaction processingterminal device, such as a magnetic stripe and/or EMV card reader. Themobile transaction processing terminal device may include other types ofinput components, including a scanner for input of bar/QR codes, andinterface to provide authentication credentials with a transactionprocessor, an RFID chip reader, a short range wireless communicationcomponent (e.g., through NFC, Bluetooth Low Energy (BLE), LTE Direct,WiFi, or other short range wireless communication protocol), or othertype of payment information input device. Thus, the transactionprocessing terminal device may correspond to a magnetic stripe, EMVchip, or other type of reader, as well as hardware necessary tointerface with the reader to determine transaction information frominput by the customer, and a communication module or component toconnect to the communication device and provide transaction informationto the communication device (e.g., through Bluetooth, BLE, WiFi, LTEDirect, NFC, or other short range communication protocol). Thetransaction processing terminal device may therefore receive input froma customer when the merchant or merchant's employee is performingcheckout and transaction processing, such as input for the customer'spayment card (e.g., a swipe of a payment card's magnetic stripe,insertion of the payment card's EMV chip, or other input). Thetransaction processing terminal device may determine the customer and/orpayment card's payment information, and may provide the transactioninformation to the connected communication device for processing (e.g.,using a backend payment processor with the communication device).

The merchant may provide a plurality of mobile transaction processingterminal devices at a merchant location. For example, a restaurant orretail location may employ one or more merchant employees to providesales to customers through the merchant location. In this regard, themobile transaction processing terminal devices may be made mobilepoint-of-sale devices instead of fixed point-of-sale devices using themerchant and/or merchant employee's (referred to herein as “merchant” or“merchants”) communication device to connect with the transactionprocessing terminal device and provide transaction processing. However,the transaction processing terminal devices may require maintenance,charging, and/or updates (e.g., software and/or firmware updates).Additionally, the merchant may require assistance in connecting thetransaction processing terminal device to the merchant's communicationdevice. For example, the merchant may be required to connect theircommunication device to the transaction processing terminal device atthe beginning of every use, where the transaction processing terminaldevice was previously disconnected from the communication device at theend of use and/or used by another user prior to use.

In order to provide maintenance and connection assistance for thetransaction processing terminal device(s) of the merchant, the merchantmay utilize a smart terminal harbor device, which may correspond to ahardware device that provides maintenance and connection services to thetransaction processing terminal device(s). The terminal harbor mayinclude a body or port structure where the transaction processingterminal device(s) may be placed, entered, or otherwise connected.Additionally, the terminal harbor may include a power source and atleast one power connector used to charge the transaction processingterminal device(s). In order to connect with the transaction processingterminal device(s) and/or one or more communication devices of themerchant, the terminal harbor may further include a communication moduleor component that may connect to the aforementioned devices. Thecommunication module may utilize wired or wireless connections to theother devices (e.g., the transaction processing terminal device(s)and/or one or more communication devices of the merchant), for example,through USB, microUSB, Lightning®, or other type of wired connection, orthrough Bluetooth, BLE, LTE Direct, WiFi, or other type of wirelessconnection.

Additionally, the terminal harbor may include a non-transitory memory,which may store one or more applications executable by the terminalharbor. The applications may include processing applications for thepayment terminal device(s) and communication devices. The processingapplications may be used to maintain, update, and charge the transactionprocessing terminal device(s), as well as establish connections betweenthe transaction processing terminal device(s) and one or morecommunication devices of the merchant. Additionally, the terminal harbormay include one or more hardware processors that execute the processingapplications. The terminal harbor may include additional hardware and/orsoftware components. For example, the terminal harbor may include anapplication usable with a network interface component of the terminalharbor's communication module to connect to a network and communicationwith one or more devices and/or servers on the network. In this regard,a service provider server available over the network may be used toprovide software and/or firmware updates to the terminal harbor, whichmay be used to install and/or update the software and/or firmware of theterminal harbor and/or the transaction processing terminal device(s).

Thus, the merchant may connect one or more transaction processingterminal devices to the terminal harbor for maintenance, updating,and/or charging. Once connected, a transaction processing terminaldevice may be scanned through a diagnostic tool of the terminal harbor,such as a tool or process of a terminal processing application. Thediagnostic tool may determine one or more conditions or statusesaffecting the transaction processing terminal device. For example, theconditions or statuses may be related to the hardware and/or software ofthe transaction processing terminal device. In this regard, a conditionor a status may be software version and/or required software updates,firmware version and/or required firmware updates, damage to softwareand/or hardware requiring maintenance or resolution, battery chargelevel, battery conditioning requirements for rechargeable batteries,graphical user interface information (e.g., display output types,effects, and/or capabilities), communication module information (e.g.,health, communication protocols, communication signal strength/distance,etc.), or other status or condition affecting the health and/orviability for usage of the transaction processing terminal device. Thediagnostic tool may run to determine the condition/status after thetransaction processing terminal device is returned to the terminalharbor, for example, after the transaction processing terminal device isused by the merchant during work and/or for transaction processing.

One the status or condition is determined; the terminal harbor maydetermine one or more processes to resolve the condition(s) of thetransaction processing terminal device. For example, the process(es) maycorrespond to a preventative maintenance of the transaction processingterminal device, a full lifecycle update, battery charging, batteryconditioning, a software update, and/or a firmware update. Theprocess(es) may also correspond to an alert to an administrator that mayfix or otherwise assist in remedying the condition(s). Additionally,other processes may also resolve the condition(s). The terminal harbormay then execute the processes with the transaction processing terminaldevice. While executing the process(es) with the transaction processingterminal device, the terminal harbor may include one or more outputdevices, which may alert other users (e.g., the merchant) that thetransaction processing terminal device is currently undergoingmaintenance. For example, the output device may include one or morelights or a small output display, where the output may alert a user thatthe transaction processing terminal device associated with the display(e.g., next to, under, or connected to) is not for use (e.g., a redlight, a “Do not use” sign, etc.).

Once the process(es) is/are completed, the output device may signal thatthe transaction processing terminal device is now good or viable foruse. For example, a light may turn to green, or the output display mayshow “Ready for use.” In other embodiments, the notification may be sentto a device or server, such as the merchant's communication deviceand/or the service provider server. In various embodiments, prior toreadying the transaction processing terminal device for use, theterminal harbor may further run the diagnostic tool to determine whetherany conditions or statuses still remain on the transaction processingterminal device. If so, the terminal harbor may repeat the process priorto resolving all conditions affecting the transaction processingterminal device. Additionally, the terminal harbor device may also run atroubleshooting or trial run tool, process, or application, which may beused to determine whether the transaction processing terminal devicewill perform adequately under performance conditions (e.g., transactionprocessing). Thus, the terminal harbor may wait to provide a “ready foruse” status for the harbor device to finish maintenance and test runningthe transaction processing terminal device.

The terminal harbor may repeat the above process for additionaltransaction processing terminal devices connected to the harbor device.Such maintenance may be performed on connection of each of thetransaction processing terminal devices to the terminal harbor, or maybe staggered so that one or more payment terminal devices are alwaysavailable for use. Additionally, as each transaction processing terminaldevice is connected to the terminal harbor and maintenance is performed,the terminal harbor may establish and update a database of transactionprocessing terminal devices, where the database may include informationon which transaction processing terminal devices are available for use,which require maintenance or are receiving maintenance, and whichtransaction processing terminal devices are unavailable (e.g., broken orrequire physical maintenance). Additionally, the database may includeinformation on time of use of each of the transaction processingterminal devices, type of use, communication devices using each of thepayment terminal devices, and/or capabilities of the communicationdevices and/or transaction processing terminal devices. The transactionprocessing terminal devices may be connected to the terminal harborthrough a wired or wireless connection, and may be detected and/orconnected for maintenance through connecting to the terminal harbor,placing in an area of the terminal harbor, and/or “tapping” orperforming an action with the terminal harbor.

The database information on the device usage and/or available devicesmay be used to determine when to service and/or perform maintenance oneach of the transaction processing terminal devices. For example, one ormore of the transaction processing terminal devices may be serviced whenthe transaction processing terminal device(s) has a “downtime” or is notin use. In one example, such downtime may occur during night or when themerchant is closed, where the merchant is not performing business andnot using the transaction processing terminal device(s) for transactionprocessing. However, other intelligent decision-making of service timemay also be utilized. In this regard, certain transaction processingterminal devices may be utilized for certain communication devices ofthe merchant, where those certain communication devices are used atcertain times (e.g., where an iPhone for a merchant is always usedbetween 10 AM-6 PM Monday-Friday). Thus, the terminal harbor maymaintain that specific transaction processing terminal device during thedowntime, and make sure that the transaction processing terminal deviceis usable between the specific times required.

At other times a schedule, such as a shift schedule, may be used todetermine how many and which transaction processing terminal devices arerequired at certain times, and when other transaction processingterminal device may be serviced. At other times, the processes requiredto perform maintenance on the transaction processing terminal device mayaffect when the transaction processing terminal device is serviced. Forexample, battery conditioning of a rechargeable battery may takeconsiderably longer than a small patch to software of the transactionprocessing terminal device. Thus, such processes may be performed duringclosed hours or where the transaction processing terminal device is notneeded. Other information may also affect when to service one or more ofthe transaction processing terminal devices, for example, current salesvolume and/or detected customers, merchant device health, health andstatus of transaction processing terminal devices currently in use, orother factors.

The terminal harbor may also be used for intelligent selection for useof a transaction processing terminal device with a requestingcommunication device. For example, a communication device may requestuse of a transaction processing terminal device. In this regard, thecommunication device may connect with the terminal harbor. Theconnection may occur through a wired or wireless connection. In variousembodiments, the request may be generated by the user of thecommunication device (e.g., the merchant), for example, through anapplication executing on the communication device. However, in otherembodiments, the request may be automatically generated when thecommunication device connects to the terminal harbor. In variousembodiments, such connection may occur automatically when the user walkswithin range of the terminal harbor with the communication device. Therequest may be processed by the terminal harbor using the information ofavailable and unavailable transaction processing terminal devices. Thus,the terminal harbor may determine an available payment terminal device,and may connect the selected transaction processing terminal device tothe communication device. For example, where the transaction processingterminal device uses a Bluetooth connection to connect with a device fortransaction processing, the terminal harbor may configure the Bluetoothconnectivity settings of the communication device and/or transactionprocessing terminal device to connect through Bluetooth (e.g., byactivating the Bluetooth connection module of both devices, causing thecommunication device to search for a signal having an identifier fromthe transaction processing terminal device, and connecting to thetransaction processing terminal device through such a signal). In otherembodiments, other connections may be established between thecommunication device and the selected/available transaction processingterminal device, including wired or wireless connections. In furtherembodiments, instructions may be output to the merchant on thecommunication device to establish the connection. Additionally, theterminal harbor device may cause an alert on an output device of theterminal harbor device that is associated with the selected transactionprocessing terminal device that notifies the user to take and use thattransaction processing terminal device. Such notification may also orinstead be displayed on the communication device.

Once connected, the merchant may use the transaction processing terminaldevice to perform transaction processing through the communicationdevice. For example, the transaction processing terminal device mayreceive transaction information input from a customer and provide theinformation to the communication device. The communication device maythen perform transaction processing through a backend payment processor,such as the service provider. In various embodiments, the transactionprocessing terminal may further provide offline transaction processing,for example, offline EMV transaction processing. In this regard, thetransaction processing terminal may lose connectivity to a backendtransaction processing entity (e.g., network, cloud, merchant device,etc.). In such embodiments, the transaction processing terminal maylocally verify the cryptogram and/or PIN provided to the transactionprocessing terminal by a user and/or input by a merchant duringtransaction processing (e.g., through payment instrument entry). Thetransaction processing terminal may provide approval and may store thetransactions to a cache. The cache may have a fixed size andavailability to store transactions (e.g., 200 transactions). The storedtransactions may be uploaded and processed on connection of thetransaction processing terminal to a network/cloud or the terminalharbor device.

During use, the transaction processing terminal device may furthermonitor the transaction processing terminal devices, for example,through the communication device and/or wireless communications with thetransaction processing terminal devices. If one transaction processingterminal device begins failing, requires an update, or otherwise shouldbe discontinued from use, the terminal harbor may notify the userthrough the transaction processing terminal device and/or thecommunication device. The terminal harbor may further select anothertransaction processing terminal device, and may notify the user of thenew transaction processing terminal device. Additionally, the terminalharbor may assist in connecting the new transaction processing terminaldevice to the communication device. Once the previous transactionprocessing terminal device is reconnected to the terminal harbor, theterminal harbor may service the transaction processing terminal deviceas previously discussed.

The terminal harbor may further provide intelligent selection of atransaction processing terminal device to pair to a communication devicethrough additional information. For example, information on amaintenance schedule of the transaction processing terminal devices maybe used to select a best transaction processing terminal device to pairwith the communication device (e.g., one that currently does not requiremaintenance or where other devices currently require maintenance). Thus,the current health, maintenance schedule, and/or statistics of thetransaction processing terminal devices may be used to select one ormore of the transaction processing terminal devices. Additionally,selection of the transaction processing terminal device may depend oncached transactions and cache size of the transaction processingterminal device. Thus, one of the parameters used to select atransaction processing terminal may be the cache size and spaceavailability, as well as required transactions for uploading andprocessing stored to a transaction processing terminal (e.g., favoringdevices with more cache availability and/or servicing transactionprocessing terminals having stored transactions). In other embodiments,the terminal harbor may select a transaction processing terminal devicebased on the compatibility of the transaction processing terminal devicewith the communication device. For example, the specification of thecommunication device may be retrieved (e.g., from the communicationdevice and/or the database based on previously stored information),where the specifications may correspond to the device type (e.g., smartphone, tablet, etc.), hardware capabilities, software capabilities,installed software, available hardware devices, operating system, orother specification. Additionally, the specifications and/orcapabilities of the transaction processing terminal may be determined.Such information may be used to determine which devices are mostcompatible. For example, an Android® type device may function betterwith a transaction processing terminal device specific to Androidspecifications.

In other embodiments, the selection may be made based on the features ofthe communication device. For example, certain transaction processingterminal devices may function better with a tablet or with a mobilesmart phone. In such embodiments, the presentation on the output displayof the communication device may affect the selection of the transactionprocessing terminal device. Other types of communication devices mayalso be used, as well as auxiliary devices of the transaction processingterminal device. For example, a transaction processing terminal devicewith an associated headset may be selected for certain communicationdevices. Moreover, the role of the merchant employee and/or the merchantemployees work information may be used to select a transactionprocessing terminal device. In this regard, the aforementionedtransaction processing terminal device with a headset may be reservedfor drive-through merchants, whereas a transaction processing terminaldevice without a headset may be selected for a merchant assistingdine-in customers. Similarly, a transaction processing terminal devicewith a full charge may be reserved for a merchant having a long shift,whereas a half charged payment terminal device may be provided to amerchant with a short shift. Similarly, the amount of use and/ortransaction processing by the merchant in the past may affect selectionof a transaction processing terminal device.

FIG. 1 is a block diagram of a networked system 100 suitable forimplementing the processes described herein, according to an embodiment.As shown, system 100 may comprise or implement a plurality of devices,servers, and/or software components that operate to perform variousmethodologies in accordance with the described embodiments. Exemplarydevices and servers may include device, stand-alone, andenterprise-class servers, operating an OS such as a MICROSOFT® OS, aUNIX® OS, a LINUX® OS, or other suitable device and/or server based OS.It can be appreciated that the devices and/or servers illustrated inFIG. 1 may be deployed in other ways and that the operations performedand/or the services provided by such devices and/or servers may becombined or separated for a given embodiment and may be performed by agreater number or fewer number of devices and/or servers. One or moredevices and/or servers may be operated and/or maintained by the same ordifferent entities.

System 100 includes a transaction processing terminal device 110, aterminal harbor device 120, a communication device 130, and a serviceprovider server 150 in communication over a network 170. A user, such asa merchant (not shown), may utilize transaction processing terminaldevice 110 to perform transaction processing with communication device130, which may utilize service provider server 150 in variousembodiments to process transactions with the merchant. Transactionprocessing terminal device 110 may interface with terminal harbor device120 for maintenance of transaction processing terminal device 110, forexample, updates, charging, and other types of device maintenance. Invarious embodiments, service provider server 150 may provide the updatesfor transaction processing terminal device 110. Once serviced, terminalharbor device 120 may make transaction processing terminal device 110available for use. Thus, later when communication device 130 requiresfurther use of transaction processing terminal device 110, terminalharbor device 120 may select transaction processing terminal device 110based on the maintenance performed on transaction processing terminaldevice 110, as well as the capabilities and/or specifications ofcommunication device 130.

Transaction processing terminal device 110, terminal harbor device 120,communication device 130, and service provider server 150 may eachinclude one or more processors, memories, and other appropriatecomponents for executing instructions such as program code and/or datastored on one or more computer readable mediums to implement the variousapplications, data, and steps described herein. For example, suchinstructions may be stored in one or more computer readable media suchas memories or data storage devices internal and/or external to variouscomponents of system 100, and/or accessible over network 170.

Transaction processing terminal device 110 may be implemented as aterminal for receiving input of transaction (e.g., payment) informationthat may utilize appropriate hardware and software configured for wiredand/or wireless communication with terminal harbor device 120 andcommunication device 130. For example, in one embodiment, transactionprocessing terminal device 110 may be implemented as a magnetic stripereader, EMV chip reader, or other types of computing devices capable oftransmitting and/or receiving data, including payment information.Transaction processing terminal device 110 may correspond be utilized bya user, such as a merchant or employee of the merchant, duringprocessing for a transaction. In this regard, transaction processingterminal device 110 may correspond to an input device that receivesinput correspond to transaction information, such as a swipe of amagnetic stripe, input of an EMV chip, or other type of input. Althoughonly one terminal device is shown, a plurality of terminal devices mayfunction similarly.

Transaction processing terminal device 110 of FIG. 1 contains terminalapplications 112, a scanner 114, a database 116, and a communicationmodule 118. Terminal applications 112 may correspond to executableprocesses, procedures, and/or applications with associated hardware. Inother embodiments, payment terminal device 110 may include additional ordifferent modules having specialized hardware and/or software asrequired.

Terminal applications 112 may correspond to one or more processes toexecute modules and associated devices of payment terminal device 110 toconnect to terminal harbor device 120 and/or communication device 130,as well as receive transaction information from a customer and providethe transaction information to communication device 130 for paymentprocessing. In this regard, terminal applications 112 may correspond tospecialized hardware and/or software utilized by transaction processingterminal device 110 to connect and/or disconnect from terminal harbordevice 120 and/or communication device 130. In this regard, terminalapplications 112 may include a communication application that mayutilize communication module 118 of transaction processing terminaldevice 110 to send and receive data signals. Terminal applications 112may establish a connection with communication device 130 using the datasignals. For example, terminal applications 112 may broadcast anidentifier, such as a universally unique identifier (UUID), which may bereceivable by terminal harbor device 120 and/or communication device130. In other embodiments, terminal applications 112 may instead receivean identifier from terminal harbor device 120 and/or communicationdevice 130. Using the identifier(s), terminal applications 112 maycommunicate with terminal harbor device 120 and/or communication device130. However, in other embodiments, a wired connection may be utilized,where terminal applications 112 may be utilized to interface withterminal harbor device 120 and/or communication device 130. Terminalapplications 112 may connect to terminal harbor device 120 for purposesof maintenance and servicing. Thus, terminal harbor device 120 mayupdate and/or troubleshoot terminal applications 112 when transactionprocessing terminal device 110 is connected to terminal harbor device120, as discussed herein. Terminal applications 112 may provideinformation on the health, statuses, and conditions for transactionprocessing terminal device 110 to terminal harbor device 120 whileconnected to terminal harbor device 120 for maintenance.

Terminal applications 112 may further include input applications andassociated processes to receive input, such as transaction informationfrom a customer. Thus, terminal applications 112 may connect withcommunication device 130 for the purposes of transaction processing. Invarious embodiments, terminal harbor device 120 may generate theconnection between transaction processing terminal device 110 andcommunication device 130. Once connected with communication device 130,payment terminal device may be used for transaction processing. Forexample, the merchant associated with communication device 130 mayprovide sales, checkout, and transaction processing services tocustomers through transaction processing terminal device 110 andcommunication device 130. In this regard, a customer in a transactionwith the merchant may provide input to transaction processing terminaldevice 110, where the input may correspond to transaction information.For example, the input may correspond to a payment card (e.g., magneticstripe, EMV chip, etc.), or may be other types of input, includingauthentication information for a payment account, or other type ofinput. Terminal applications 112 may receive the input through an inputmechanism of transaction processing terminal device 110 (e.g., scanner114). In various embodiments, terminal applications 112 may determinethe transaction information from the input. Terminal applications 112may provide the transaction information to communication device 130 fortransaction processing. Thus, terminal applications 112 may interfacewith one or more applications of communication device 130 to provide thetransaction information. Once completed with the transaction, terminalapplications 112 may provide further transaction processing, forexample, through additional input for further transactions.Additionally, terminal applications 112 may be used to provide health,statuses, and conditions of transaction processing terminal device 110to terminal harbor device 120 during use of transaction processingterminal device 110. Additionally, terminal applications 112 may befurther provide processes to disconnect from communication device 130after usage of transaction processing terminal device 110.

In various embodiments, terminal applications 112 include otheradditional applications as may be desired in particular embodiments toprovide features to transaction processing terminal device 110. Forexample, terminal applications 112 may include security applications forimplementing client-side security features, programmatic clientapplications for interfacing with appropriate application programminginterfaces (APIs) over network 170, or other types of applications.Terminal applications 112 may also include additional communicationapplications that allow a user to send and receive payment informationand other data between devices. Other applications 114 may includedevice interface applications that may receive input and/or outputinformation. For example, other applications 114 may contain softwareprograms, executable by a processor, including a graphical userinterface (GUI) configured to provide an interface to the user.

Transaction processing terminal device 110 further includes a scanner114, which may correspond to an input device or mechanism of paymentterminal device 110. In this regard, scanner 114 may correspond to amagnetic stripe reader, an EMV chip reader, an RFID scanner, a shortrange communication module, or other type of input device that may readdata from a physical object provided to the merchant by a customer forprocessing a transaction between the merchant and the customer. In otherembodiments, scanner 114 may instead or further correspond to othertypes of input devices, including a keypad, keyboard, touch screeninterface, or other input device capable of receiving paymentinformation (e.g., a username, password, PIN or other authenticationmechanism). Scanner 114 may be used by terminal applications 112 toreceive data corresponding to the transaction information.

Transaction processing terminal device 110 may further include database116 stored to a transitory and/or non-transitory memory of transactionprocessing terminal device 110, which may store various applications anddata and be utilized during execution of various modules of transactionprocessing terminal device 110. Thus, database 116 may include, forexample, identifiers (IDs) such as IDs associated with hardware oftransaction processing terminal device 110 or other appropriate IDs.Database 116 may include data for payment information, as well asinformation on conditions and/or statuses of transaction processingterminal device 110. In various embodiments, the transaction informationand information on the conditions and/or statues of transactionprocessing terminal device 110 may be provided to one or more ofterminal harbor device 120 and/or communication device 130.

Transaction processing terminal device 110 includes at least onecommunication module 118 adapted to communicate with terminal harbordevice 120 and/or communication device 130. In various embodiments,communication module 118 may include a DSL (e.g., Digital SubscriberLine) modem, a PSTN (Public Switched Telephone Network) modem, anEthernet device, a broadband device, a satellite device and/or variousother types of wired and/or wireless network communication devicesincluding microwave, radio frequency, infrared, Bluetooth, and nearfield communication devices.

Terminal harbor device 120 may be implemented as a docking, port, orharbor device that may utilize appropriate hardware and softwareconfigured for wired and/or wireless communication with transactionprocessing terminal device 110, communication device 130, and/or serviceprovider server 150. For example, in one embodiment, communicationdevice 130 may be implemented as a personal computer (PC), dockingdevice, and/or other types of computing devices capable of transmittingand/or receiving data. Terminal harbor device 120 may be utilized by amerchant to intelligently service transaction processing terminaldevices, such as transaction processing terminal device 110, as well asprovide intelligent selection of one of the transaction processingterminal devices for pairing with communication device 130. Althoughonly one terminal harbor device is shown, a plurality of terminal harbordevices may function similarly.

Communication device 130 of FIG. 1 contains a terminal processingapplication 122, a device processing application 124, a database 126,and a communication module 128. Terminal processing application 122 anddevice processing application 124 may correspond to executableprocesses, procedures, and/or applications with associated hardware. Inother embodiments, terminal harbor device 120 may include additional ordifferent modules having specialized hardware and/or software asrequired.

Terminal processing application 122 may correspond to one or moreprocesses to execute modules and associated devices of terminal harbordevice 120 to connect to one or more transaction processing terminaldevices, such as transaction processing terminal device 110, performmaintenance and servicing of the transaction processing terminaldevice(s), and connect transaction processing terminal device 110 tocommunication device 130 based on the health of transaction processingterminal device 110 and the specifications of communication device 130.In this regard, terminal processing application 122 may correspond tospecialized hardware and/or software utilized by terminal harbor device120 to first connect to transaction processing terminal device 110.Terminal processing application 122 may connect to transactionprocessing terminal device 110 through a wired or wireless connection.For example, terminal harbor device 120 may connect with transactionprocessing terminal device 110 through a USB, microUSB, Lightning®, orother wired connection, where terminal processing application 122 mayinterface with one or more APIs executing on transaction processingterminal devices 110 in order to perform the aforementioned features.However, in other embodiments, terminal harbor device 120 may connectwith transaction processing terminal device 110 through a wirelessconnection, such as Bluetooth, BLE, NFC, LTE Direct, WiFi, or othershort range communication protocol. In order to connect over a wirelessconnection, terminal processing application 122 may broadcast anidentifier receivable by payment terminal device 110 over a short rangeproximity to terminal harbor device, such as a signal strength for shortrange wireless communications. Transaction processing terminal device110 may receive the identifier, and use the identifier to establish acommunication channel and/or exchange data. In other embodiments,transaction processing terminal device 110 may broadcast the identifier,where terminal processing application 122 may similarly receive theidentifier and use the identifier to open and establish a communicationchannel with transaction processing terminal device 110 and/or exchangedata. Thus, payment terminal device 110 may connect with terminal harbordevice 120 when in proximity to terminal harbor device 120, for example,when transaction processing terminal device 110 is place on, nearby, orin terminal harbor device 120.

Once connected, terminal processing application 122 may determine one ormore conditions or statuses affecting transaction processing terminaldevice 110. For example, terminal processing application 122 may executea diagnostic tool or process which scans transaction processing terminaldevice 110 to determine at least one condition (e.g., the health of thesoftware and/or hardware, versions of the software and/or hardwarerequiring update, require maintenance and/or conditioning, etc.) fortransaction processing terminal device 110. The condition(s) may affectthe operability of transaction processing terminal device 110, or may berequired for further use of transaction processing terminal device 110.For example, the condition(s) may correspond to a power level or batterycondition, out of date software/firmware, damage to software and/orhardware, and/or new software for use with transaction processingterminal device 110. Additional conditions may also affect the healthand/or operability of transaction processing terminal device 110.

Once the condition(s) of transaction processing terminal device 110 aredetermined, terminal processing application 122 may determine at leastone process to execute with transaction processing terminal device 110to remedy or resolve the condition(s) so that the condition(s) no longeraffect transaction processing terminal device 110. Terminal processingapplication 122 may determine the process(es) based on the condition asone or more instructions to resolve the condition(s) stored to database126 and/or available with service provider server 150. For example, theprocess(es) may correspond to a charging instruction, batteryconditioning, preventive maintenance, update process for software and/orfirmware, and/or other processes for fixing, servicing, updating, and/orcharging transaction processing terminal device 110. Once theprocess(es) is/are determined, terminal processing application 122 mayexecute the process(es) with transaction processing terminal device 110.Additionally, terminal processing application 122 may further executethe diagnostic tool to determine if further conditions requireresolution, and/or may execute a troubleshooting/test run process orapplication to determine whether transaction processing terminal device110 is ready for use.

Terminal processing application 122 may include processes to updateoutput displays and/or database 126 with information of availabletransaction processing terminal devices. For example, terminalprocessing application 122 may change output displays, such as LEDs orother signal lights, which may indicate whether payment terminal device110 is available for use. For example, where transaction processingterminal device 110 is unavailable (e.g., when maintenance processes,such as the diagnostic tool and/or processes determined to resolveconditions, are executing), an output display may show a red light ordisplay “Unavailable” or “Do not use.” However, where transactionprocessing terminal device 110 is available, the output display may showa green light or display “Available” or “Ready for use.” Additionally,database 126 may include data entries (e.g., table entries in a databasetable for available and unavailable transaction processing terminaldevices) that indicate which transaction processing terminal devices areavailable and unavailable, which may further include identifiersreceivable by one or more other devices indicating the availability ofthe transaction processing terminal devices.

Additionally, terminal processing application 122 may determine when toperform the processes with transaction processing terminal device 110and/or other transaction processing terminal devices. For example,terminal processing application 122 may determine and/or receive data onusage of transaction processing terminal devices, including transactionprocessing terminal device 110. The usage may correspond to times ofusage, types of usage, schedules for usage, or other information on therequired availability of the transaction processing terminal devices. Inthis regard, usage information for transaction processing terminaldevice 110 may be determined by monitoring the usage of transactionprocessing terminal device 110 and/or receiving input about the usage oftransaction processing terminal device 110 from the merchant and/or andadministrator of terminal harbor device 120. Using the usageinformation, terminal processing application 122 may determine when toperform the process(es) to resolve the issues of transaction processingterminal device 110. For example, a time to perform the processes and/orupdate transaction processing terminal device 110 may correspond todowntime in usage of transaction processing terminal device 110 and/orother transaction processing terminal devices. Thus, the time may beselected to insure that transaction processing terminal device 110 isavailable when required.

Terminal processing application 122 may also receive a request toconnect to a transaction processing terminal device. The request may beoriginated by communication device 130, for example, on connection ofcommunication device 130 to terminal harbor device 120. Communicationdevice 130 may connect to terminal harbor device 120 using a wired orwireless connection. For example, communication device 130 may connectto terminal harbor device 120 through a USB, microUSB, Lightning®, orother communication port. Once connected terminal processing application122 may interface with communication device 130, where a request toconnect transaction processing terminal device 110 to communicationdevice 130 for payment processing may be generated. The request may begenerated by communication device 130, for example, on connection toterminal harbor device 120 or based on input by the merchant tocommunication device 130. In other embodiments, on detection ofcommunication device 130 connecting to terminal harbor device 120,terminal processing application 122 may generate the request. In otherembodiments, terminal harbor device 120 and communication device 130 mayconnect through a wireless connection, such as Bluetooth, BLE, NFC, LTEDirect, WiFi, or other short range communication protocol. In order toconnect over a wireless connection, terminal processing application 122may broadcast an identifier receivable by communication device 130 overa short range proximity to terminal harbor device, such as a signalstrength for short range wireless communications. Communication device130 may receive the identifier, and use the identifier to establish acommunication channel and/or exchange data. In other embodiments,communication device 130 may broadcast the identifier, where terminalprocessing application 122 may similarly receive the identifier and usethe identifier to open and establish a communication channel withcommunication device 130 and/or exchange data. Thus, communicationdevice 130 may connect with terminal harbor device 120 when in proximityto terminal harbor device 120, for example, when communication device130 is place on, nearby, or in terminal harbor device 120.

Once the request is generated, terminal harbor device 120 may select atransaction processing terminal device of the one or more transactionprocessing terminal devices available to terminal harbor device 120,such as transaction processing terminal device 110. For example,terminal harbor device 120 may select transaction processing terminaldevice 110 after servicing transaction processing terminal device 110and when transaction processing terminal device 110 is available for useas indicated in database 126. Thus, terminal processing application 122may select a transaction processing terminal device based on itsavailability and after performing maintenance/servicing on thetransaction processing terminal device. Moreover, terminal processingapplication 122 may select payment terminal device 110 over anotheravailable payment terminal device, for example, where the othertransaction processing terminal device may require further maintenance(e.g., additional charging, updating of software/firmware, etc.). Thus,terminal processing application 122 may intelligently select atransaction processing terminal device to pair to communication device130 on request based on the maintenance and availability of each of thetransaction processing terminal devices available to terminal harbordevice 120.

In further embodiments, terminal harbor device 120 may also or insteadselect transaction processing terminal device 110 based on devicecapabilities and specifications of communication device 130. Thecapabilities and/or specifications may correspond to a device type,brand, available hardware, available software, and/or other processes orfeatures of communication device 130. Additionally, the capabilitiesand/or specifications of transaction processing terminal device 110 mayfurther be used to select transaction processing terminal device 110.Transaction processing terminal device 110 may be selected for an easeof use with communication device 130, an ease or feasibility ofconnection between transaction processing terminal device 110 andcommunication device 130, and/or a compatibility of transactionprocessing terminal device 110 with communication device 130. Thecompatibility may be determined based on the features and/or processesof transaction processing terminal device 110 and communication device130. In various embodiments, transaction processing terminal device 110may further be selected based on the merchant associated withcommunication device 130 and/or the usage of communication device 130for transaction processing. For example, based on the merchant's roleand/or schedule, transaction processing terminal device 110 may beselected as a “best fit” or most preferable. Such selection may furtherdepend on the condition and/or capabilities of transaction processingterminal device 110, include auxiliary devices of transaction processingterminal device 110 (e.g., a headset with earphones and a microphone, aspecific input/display device, etc.). Transaction processing terminaldevice 110 may be selected based on the amount of time or the specifictimes that the merchant requires transaction processing terminal device110. Transaction processing terminal device 110 may also be selectedbased on the time and length of usage with communication device 110.Such information may be determined based on past usage, or may be inputby the merchant. The merchant may the use transaction processingterminal device 110 for transaction processing with communication device130, as discussed herein. Once the merchant associated withcommunication device 130 is completed with using transaction processingterminal device 110, transaction processing terminal device 110 may bereturned to terminal harbor device 120. For example, the merchant mayconnect transaction processing terminal device 110 back to terminalharbor device 120. Once connected, terminal processing application 122may perform maintenance and servicing, as discussed above.

Device processing application 124 may correspond to one or moreprocesses to execute modules and associated devices of terminal harbordevice 120 to determine device capabilities and/or usage ofcommunication device 130, and provide the information to terminalprocessing application 122. In this regard, device leasing application132 may correspond to specialized hardware and/or software utilized byterminal processing application 122 to retrieve and/or determine deviceand usage information for communication device 130. In variousembodiments, device processing application 124 may determine the devicecapabilities and specifications from scanning communication device 130and/or retrieving data from a server, such as a look-up of device datafor communication device 130. In other embodiments, such data may bestored to database 126 for one or more communication devices, which maybe retrievable by device processing application 124. The information maybe determined using an identifier for communication device 130 and/orthe hardware/software of communication device 130, or other dataidentifying the features and/or process of communication device 130.Additionally, device processing application 124 may further determineusage requirements or other information for communication device 130related to payment processing. For example, the usage requirements maycorrespond to required usage of communication device 130 with paymentterminal device 110. Thus, the usage requirements may includeinformation about sales, checkout, and transaction processing by themerchant associated with communication device 130. Such information maybe determined based on past usage of communication device 130 withpayment terminal device 110, or may be received from input by themerchant or an administrator of terminal harbor device 120.

Terminal harbor device 120 may further include database 126 stored to atransitory and/or non-transitory memory of terminal harbor device 120,which may store various applications and data and be utilized duringexecution of various modules of communication device 130. Thus, database126 may include, for example, identifiers (IDs) such as operating systemregistry entries, cookies associated with device processing application124 and/or other applications 134, IDs associated with hardware ofterminal harbor device 120, or other appropriate IDs, such as IDs oftransaction processing terminal device 110 and/or communication device130. Database 126 may include conditions and/or statuses of one or moretransaction processing terminal devices, such as transaction processingterminal device 110, as well as processes for resolution of conditionsand/or statuses. Additionally, database 126 may further includemaintenance information such as a database of available and/orunavailable transaction processing terminal devices. Additionally,information used for selection of transaction processing terminal device110 to pair with communication device 130 may be stored to database 126,such as required usage information of transaction processing terminaldevice 110 by communication device 130.

Terminal harbor device 120 includes at least one communication module128 adapted to communicate with transaction processing terminal device110, communication device 130, and/or service provider server 150. Invarious embodiments, communication module 128 may include a DSL (e.g.,Digital Subscriber Line) modem, a PSTN (Public Switched TelephoneNetwork) modem, an Ethernet device, a broadband device, a satellitedevice and/or various other types of wired and/or wireless networkcommunication devices including microwave, radio frequency, infrared,Bluetooth, and near field communication devices.

Communication device 130 may be implemented as a communication devicethat may utilize appropriate hardware and software configured for wiredand/or wireless communication with transaction processing terminaldevice 110, terminal harbor device 120, and/or service provider server150. For example, in one embodiment, communication device 130 may beimplemented as a personal computer (PC), a smart phone, laptop/tabletcomputer, wristwatch with appropriate computer hardware resources,eyeglasses with appropriate computer hardware (e.g., GOOGLE GLASS®),other type of wearable computing device, implantable communicationdevices, and/or other types of computing devices capable of transmittingand/or receiving data, such as an IPAD® from APPLE®. Communicationdevice 130 may correspond to and be utilized by a merchant fortransaction processing based on received transaction data fromtransaction processing terminal device 110. Although only onecommunication device is shown, a plurality of communication devices mayfunction similarly.

Communication device 130 of FIG. 1 contains a terminal interfaceapplication 140, a sales application 132, other applications 134, adatabase 136, and a communication module 138. Terminal interfaceapplication 140, sales application 132, and other applications 134 maycorrespond to executable processes, procedures, and/or applications withassociated hardware. In other embodiments, communication device 130 mayinclude additional or different modules having specialized hardwareand/or software as required.

Terminal interface application 140 may correspond to one or moreprocesses to execute modules and associated devices of communicationdevice 130 to interface with transaction processing terminal device 110to receive transaction information, for example, by connecting withtransaction processing terminal device 110. In this regard, deviceleasing application 132 may correspond to specialized hardware and/orsoftware utilized by communication device 130 to establish a connectionwith transaction processing terminal device 110. The connection maycorrespond to a wired connection, where data is exchanged through aphysical connection, such as a USB, microUSB, Lightning®, or otherconnection. Thus, terminal interface application 140 may interface withone or more applications of transaction processing terminal device 110through one or more APIs. In other embodiments, terminal interfaceapplication 140 may connect with payment terminal device 110 through awireless connection, such as Bluetooth, BLE, NFC, LTE Direct, WiFi, orother short range wireless communication protocol. In such embodiments,terminal interface application 140 may broadcast an identifierreceivable by transaction processing terminal device 110 or may bereceive an identifier for payment terminal device 110, where theidentifier may be used to establish a connection between transactionprocessing terminal device 110 and communication device 130 and/orexchange data. In various embodiments, terminal interface application140 may similarly connect with terminal harbor device 120 request use oftransaction processing terminal device 110, as well as establish aconnection with transaction processing terminal device 110.Additionally, after connecting with transaction processing terminaldevice 110, terminal interface application 140 may receive data fromtransaction processing terminal device 110, such as transactioninformation (e.g., payment card information, such as a credit/debit cardnumber and backend processing gateway, as well as authenticationinformation, such as a username, password, or PIN). Terminal interfaceapplication 140 may provide the transaction information to salesapplication 132 for processing.

Sales application 132 may correspond to one or more processes to executemodules and associated specialized hardware of communication device 130that provide sales, checkout, and payment processes for a transaction topurchase one or more items for sale from the merchant corresponding tocommunication device 130. In this regard, sales application 132 maycorrespond to specialized hardware and/or software of communicationdevice 130 to provide a convenient interface to permit a merchant toenter, view, and/or edit items and/or services for purchase by user 102.For example, sales application 132 may be implemented as an applicationhaving a user interface enabling the merchant to enter item informationand request payment for a transaction on checkout/payment of one or moreitems/services. In certain embodiments, sales application 132 maycorrespond more generally to a web browser configured to viewinformation available over the Internet or access a websitecorresponding to the merchant and/or payment provider server 140. Thus,sales application 132 may provide item sales through an onlinemarketplace using the website of the merchant. Thus, a merchant usingtransaction processing terminal device 110 with communication device 130may process a transaction using sales application 132.

Once a payment amount is determined for a transaction for items to bepurchased by a customer, the merchant may request payment from thecustomer, for example, through transaction information input totransaction processing terminal device 110. The provided transactioninformation may be communicated to communication device 130 with thetransaction and transaction information for approval by transactionprocessing terminal device 110. A service provider server, such asservice provider server 150, may process the transaction with theprovided transaction information and determine whether to approve ordecline the transaction using a payment instrument for the paymentprocess used with the acceptance mechanism. Sales application 132 maythen receive the results of the transaction processing, and complete thetransaction with the customer, for example, by providing the customerthe items for the transaction or declining the transaction where thecustomer is not authenticated or the transaction is not authorized(e.g., insufficient funds). As discussed herein, transaction processingterminal device 110 may be used to initiate and process the transaction.

Communication device 130 includes other applications 134 as may bedesired in particular embodiments to provide features to communicationdevice 130. For example, other applications 134 may include securityapplications for implementing client-side security features,programmatic client applications for interfacing with appropriateapplication programming interfaces (APIs) over network 170, or othertypes of applications. Other applications 134 may also include email,texting, voice and IM applications that allow a user to send and receiveemails, calls, texts, and other notifications through network 170. Invarious embodiments, other applications 134 may include financialapplications, such as banking, online payments, money transfer, or otherapplications associated with communication device 130. Otherapplications 134 may contain software programs, executable by aprocessor, including a graphical user interface (GUI) configured toprovide an interface to the user.

Communication device 130 may further include database 136 which mayinclude, for example, identifiers such as operating system registryentries, cookies associated with sales application 132 and/or otherapplications 134, identifiers associated with hardware of communicationdevice 130, or other appropriate identifiers, such as identifiers usedfor payment/user/device authentication or identification. Identifiers indatabase 136 may be used by a payment/credit provider to associatecommunication device 130 with a particular account maintained by thepayment/credit provider. Database 136 may further include paymentinformation, transaction information, and/or results.

Communication device 130 includes at least one communication module 138adapted to communicate with transaction processing terminal device 110,terminal harbor device 130, and/or service provider server 150. Invarious embodiments, communication module 138 may include a DSL (e.g.,Digital Subscriber Line) modem, a PSTN (Public Switched TelephoneNetwork) modem, an Ethernet device, a broadband device, a satellitedevice and/or various other types of wired and/or wireless networkcommunication devices including microwave, radio frequency, infrared,Bluetooth, and near field communication devices.

Service provider server 150 may be maintained, for example, by an onlineservice provider, which may maintenance services for transactionprocessing terminal devices, as well as transaction processing with amerchant. In this regard, service provider server 150 includes one ormore processing applications which may be configured to interact withtransaction processing terminal device 110, terminal harbor device 120,communication device 130, and/or another device/server to facilitateleasing of devices. In one example, service provider server 150 may beprovided by PAYPAL®, Inc. of San Jose, Calif., USA. However, in otherembodiments, service provider server 150 may be maintained by or includea financial service provider, social networking service, email ormessaging service, media sharing service, and/or other service provider,which may provide device leasing services, for example, for the use ofan application and/or account.

Service provider server 150 of FIG. 1 includes a terminal maintenanceapplication 160, a service provider application 152, other applications154, a database 156, and a network interface component 158. Terminalmaintenance application 160, service provider application 152, and otherapplications 154 may correspond to executable processes, procedures,and/or applications with associated hardware. In other embodiments,service provider server 150 may include additional or different moduleshaving specialized hardware and/or software as required.

Terminal maintenance application 160 may correspond to one or moreprocesses to execute modules and associated specialized hardware ofservice provider server 150 to provide maintenance processes and datafor use in servicing transaction processing terminal device 110 byterminal harbor device 120. In this regard, terminal maintenanceapplication 160 may correspond to specialized hardware and/or softwareto receive a request for process(es) and/or data to service transactionprocessing terminal device 110 from terminal harbor device 120. Forexample, terminal harbor device 120 may request information on how toservice and/or maintain transaction processing terminal device 110 basedon detected conditions and/or statuses of payment terminal device 110 byterminal harbor device 120. The information may correspond to one ormore processes to resolve the detected conditions and/or statuses. Inother embodiments, terminal harbor device 120 may request updates,patches, or other software/firmware that may be used with a process toservice transaction processing terminal device 110. Terminal maintenanceapplication 160 may provide the information to terminal harbor device120 over network 170. Additionally, terminal maintenance application 160may be used to update terminal harbor device 120 with new processes toresolve conditions or statuses of transaction processing terminaldevices, such as software, firmware, or other data used in servicingtransaction processing terminal devices.

Service provider application 152 may correspond to one or more processesto execute modules and associated specialized hardware of serviceprovider server 150 to provide services to a merchant, such as receivingand/or transmitting information for establishing an account or utilizinganother service of service provider server 150. In this regard, serviceprovider application 152 may correspond to specialized hardware and/orsoftware to establish an account, for example, a payment account, whichmay be utilized to send and receive payments and monetary transfers andengage in other financial transactions. A user, such as a merchant,associated with communication device 130 may establish an account withservice provider application 152 by providing personal and/or financialinformation to service provider server 150 and selecting an accountlogin, password, and other authentication information. The account maybe accessed and/or used through a browser application and/or dedicatedpayment application executed by payment terminal device 110. In order toauthenticate an identity of the merchant and/or for use of the account,service provider application 152 may authenticate the merchant for useof the account and/or identity. Once authenticated, service providerapplication 152 may be utilized to use various services provided byservice provider server 150, such as payment services or other availableservice. Service provider application 152 may then process payments tothe merchant through received payment information in a transaction fromcommunication device 130. Payments may be provided using the paymentinformation to the payment account for the merchant.

In various embodiments, service provider server 150 includes otherapplications 154 as may be desired in particular embodiments to providefeatures to service provider server 150. For example, other applications154 may include security applications for implementing server-sidesecurity features, programmatic client applications for interfacing withappropriate application programming interfaces (APIs) over network 170,or other types of applications. Other applications 154 may containsoftware programs, executable by a processor, including a graphical userinterface (GUI), configured to provide an interface to the user whenaccessing payment provider server 134. In various embodiments where notprovided by service provider application 152, other applications 154 mayinclude connection and/or communication applications.

Additionally, service provider server 150 includes database 156.Accounts in database 156 may include entity information, such as name,address, birthdate, payment/funding information, additional userfinancial information, and/or other desired user data. The entity maylink to their respective accounts through an account, user, merchant,and/or device ID, as well as a generated token, which may be provided tocommunication device 130 for use. Thus, when an ID is transmitted toservice provider server 150, e.g., from transaction processing terminaldevice 110, an account belonging to the entity may be found. Additionaldata used in servicing transaction processing terminal device 110 andother terminals, such as processes and associated data, may be stored todatabase 156.

In various embodiments, service provider server 150 includes at leastone network interface component 158 adapted to communicate withtransaction processing terminal device 110, terminal harbor device 120,and/or communication device 130 over network 170. In variousembodiments, network interface component 158 may comprise a DSL (e.g.,Digital Subscriber Line) modem, a PSTN (Public Switched TelephoneNetwork) modem, an Ethernet device, a broadband device, a satellitedevice and/or various other types of wired and/or wireless networkcommunication devices including microwave, radio frequency (RF), andinfrared (IR) communication devices.

Network 170 may be implemented as a single network or a combination ofmultiple networks. For example, in various embodiments, network 170 mayinclude the Internet or one or more intranets, landline networks,wireless networks, and/or other appropriate types of networks. Thus,network 170 may correspond to small scale communication networks, suchas a private or local area network, or a larger scale network, such as awide area network or the Internet, accessible by the various componentsof system 100.

FIG. 2A is an exemplary smart harbor device for intelligent updating andselection for use of transaction processing terminal devices, accordingto an embodiment. Environment 200 a of FIG. 2A includes terminal harbordevice 120, for example, an exemplary embodiment of terminal harbordevice 120 discussed in reference to environment 100 of FIG. 1.

An exemplary structure of terminal harbor device 120 is shown inenvironment 200 a of FIG. 2A. In other embodiments, differentstructures, body shapes, and/or ports may be used for terminal harbordevice 120. Terminal harbor device 120 is shown with a body or portstructure 1000, which includes a docking port 1000 a. Docking port 1000a may be configured to accept one or more transaction processingterminal devices, such as one or more of transaction processing terminaldevices 110 a-e. In this regard, docking port 1000 a may be configuredas a shelf, port, or other structure with transaction processingterminal devices 110 a-e may be placed, inserted, connected to orotherwise associated with terminal harbor device 120. Once placed ondocking port 1000 a, terminal harbor device 120 may connect withtransaction processing terminal devices 110 a-e in order to providemaintenance and servicing of payment terminal devices 110 a-e, includingcharging, repairing, updating, or otherwise resolving issues,conditions, and/or statuses of transaction processing terminal devices110 a-e.

In this regard, terminal harbor device 120 includes a power supply 1006,where power may be provided to hardware of terminal harbor device 120,which may be used during the execution of software and associatedprocesses of terminal harbor device 120. Power supply 1006 may alsoprovide necessary power to charge transaction processing terminaldevices 110 a-e. For example, docking port 1000 a may include one ormore charging mechanism for transaction processing terminal devices 110a-e. The charging mechanism may correspond to wired charging through awired connection, such as a USB, microUSB, Lightning®, or otherconnection. In other embodiments, the charging mechanism may bewireless, such as wireless inductive charging using an inductive coil indocking port 1000 a. In other embodiments, where transaction processingterminal devices 110 a-e include removable batteries, docking port 1000a may include a removable battery charger through a wired connection orwireless charging (e.g., inductive charging).

Terminal harbor device 120 further includes one or more connection portsor interfaces, which may be utilized as a communication module tointerface with one or more communication devices of a merchant ormerchants. For example, terminal harbor device 120 includes a wiredconnection port 1002 b which may be used to connect through a wiredconnection with a communication device of a merchant. Additionally,terminal harbor device 120 includes a wireless interface 1002 a, whichmay generate wireless connections with one or more communicationdevices. Using a connection with a communication device, terminal harbordevice 120 may select one of transaction processing terminal devices 110a-e for use with the communication device based on the availability oftransaction processing terminal devices 110 a-e and the capabilities ofthe communication device.

Additionally, terminal harbor device 120 includes one or morenotification lights, which may notify users (e.g., merchants) of theavailability of transaction processing terminal devices 110 a-e and/orwhich transaction processing terminal device of transaction processingterminal devices 110 a-e has been connected to the users' communicationdevices. For example, lights 1004 a-e are shown with two exemplarydisplay lights. Lights 1004 a-e may change color in response to theavailability of transaction processing terminal devices 110 a-e, forexample, which have been serviced and/or charged, and which requirefurther servicing, charging, or other maintenance. Additionally, as amerchant connects a communication device to terminal harbor device 120,one of lights 1004 a-e associated with the selected transactionprocessing terminal device from transaction processing terminal devices110 a-e may light up in response to the selection to alert the merchantwhich of transaction processing terminal devices 110 a-e to remove andutilize.

FIG. 2B is an exemplary environment displaying use of a transactionprocessing terminal device synchronized from a smart harbor device,according to an embodiment. Environment 200 b of FIG. 2B includesterminal harbor device 120, for example, an exemplary embodiment ofterminal harbor device 120 discussed in reference to environment 100 ofFIG. 1. Environment 200 b further includes transaction processingterminal devices 110 a-b not in use and a payment terminal device 110 cin use, all corresponding generally to transaction processing terminaldevice 110 discussed in reference to environment 100 of FIG. 1.Additionally, environment 200 b includes a communication device 130 acorresponding generally to communication device 130 discussed inreference to environment 100 of FIG. 1.

In environment 200 b, a merchant 102 a is utilizing communication device130 a to perform transaction processing using transaction processingterminal 110 c as an input device to receive payment information from acustomer during transaction processing with the customer. In thisregard, terminal harbor device 120 may be utilized to select transactionprocessing terminal device 110 c and pair transaction processingterminal device 110 c to communication device 130 a. For example,payment terminal device 110 c may be selected as transaction processingterminal devices 110 a-b are being serviced by terminal harbor device120, and thus still connected to terminal harbor device 120. In thisregard, as transaction processing terminal devices 110 a-v may berequired by other merchants, transaction processing terminal devices 110a-b may only be receiving charging maintenance or other minormaintenance, and may still be available for use. Additionally,transaction processing terminal device 110 c may also or instead beselected based on the compatibility of transaction processing terminaldevice 110 c with communication device 130 a. Such selection may occurat the start of merchant 102 a's shift, for example, at 5:00 PM shown intime 1100. Thus, when merchant 102 a finishes their shift and returnstransaction processing terminal device 110 c to terminal harbor device120, for example, at 1:00 AM shown in time 1200 of FIG. 2C, transactionprocessing terminal device 110 c may be serviced along with transactionprocessing terminal devices 110 a-b.

FIG. 2C is an exemplary environment displaying updating of paymenttransaction processing devices using a smart harbor device, according toan embodiment. Environment 200 c of FIG. 2C includes terminal harbordevice 120, for example, an exemplary embodiment of terminal harbordevice 120 discussed in reference to environment 100 of FIG. 1.Environment 200 c further includes transaction processing terminaldevices 110 a-c not in use, all corresponding generally to transactionprocessing terminal device 110 discussed in reference to environment 100of FIG. 1.

In environment 200 c, all of transaction processing terminal devices 110a-c have been returned to terminal harbor device 120. At time 1200, 1:00AM, the merchant location corresponding to environment 200 c may beclosed, and none of transaction processing terminal devices 110 a-c maybe required for use. In this regard, terminal harbor device 120 mayexecute lengthy maintenance procedures on transaction processingterminal devices 110 a-c that would normally make transaction processingterminal devices 110 a-c unavailable for an extended period of time. Forexample, software updates and/or patches may be installed, firmware maybe updated, battery conditioning may occur on rechargeable batteries, orother process necessary to remedy or resolve any condition or statusaffecting transaction processing terminal devices 110 a-c may beperformed. Thus, at 9:00 AM shown in time 1300 of FIG. 2D, transactionprocessing terminal devices 110 a-c may be ready for use and fullyserviced.

FIG. 2D is an exemplary environment displaying selection of atransaction processing terminal device for connection to a mobilecommunication device by a smart harbor device, according to anembodiment. Environment 200 d of FIG. 2D includes terminal harbor device120, for example, an exemplary embodiment of terminal harbor device 120discussed in reference to environment 100 of FIG. 1. Environment 200 dfurther includes transaction processing terminal devices 110 a-c not inuse, all corresponding generally to transaction processing terminaldevice 110 discussed in reference to environment 100 of FIG. 1.Additionally, environment 200 d includes a communication device 130 bcorresponding generally to communication device 130 discussed inreference to environment 100 of FIG. 1.

In environment 200 d, a second merchant, a merchant 102 b, begins theirshift and requires use of one of transaction processing terminal devices110 a-c for use with communication device 130 b during paymentprocessing for a transaction (e.g., to enter payment information from acustomer). Thus, merchant 102 b may connect communication device 130 bto terminal harbor device 120 through a wired and/or wirelessconnection, and may request use of one of transaction processingterminal devices 110 a-c. Once connected, terminal harbor device 120 mayselect one of transaction processing terminal devices 110 a-c based onthe maintenance history, status, and/or availability of transactionprocessing terminal devices 110 a-c, as well as the compatibility ofpayment terminal devices 110 a-c with communication device 130 b (e.g.,based on the capabilities and/or specifications of transactionprocessing terminal devices 110 a-c and communication device 130 b).

FIG. 3 is an exemplary system environment having interacting devices foruse of a smart harbor device for intelligent updating and selection foruse of transaction processing terminal devices, according to anembodiment. Environment 300 of FIG. 3 includes a transaction processingterminal device 110, a terminal harbor device 120, and a communicationdevice 130 corresponding generally to the described devices andassociated features found in system 100 of FIG. 1.

Transaction processing terminal device 110 executes terminalapplications 112 corresponding generally to the specialized hardwareand/or software modules and processes described in reference to FIG. 1.In this regard, terminal applications 112 including information forconditions, health, and/or statuses of transaction processing terminaldevice 110, as well as software processes used in transactionprocessing, and connected devices to send transaction information duringprocessing. Thus, terminal applications 112 include at least readerprocesses 2000 used to read payment data from a payment instrument, suchas a debit or credit card having a magnetic stripe and/or EMV chip.Thus, reader processes 2000 may include reader data, such as the paymentdata read from the payment instrument. Additionally, terminalapplications 112 may further include device data 2004 on the conditions,health, and/or statuses of transaction processing terminal device 110.For example, device data 2004 may include hardware status 2006, softwarestatues 2008, and/or battery status 2010. Additional information mayalso be associated with device data 2004 in further embodiments.

Terminal harbor device 120 executes terminal processing application 122corresponding generally to the specialized hardware and/or softwaremodules and processes described in reference to FIG. 1. In this regard,terminal processing application 122 may be used to service one or moretransaction processing terminal devices, including transactionprocessing terminal device 110, and connect transaction processingterminal device to communication device 130 on request by communicationdevice 130. Thus, terminal processing application 122 includesinformation for transaction processing terminals 2100 connected toterminal harbor device 120, such as connected terminals 2102. Forconnected terminals 2102, terminal processing application 122 mayfurther determine required maintenance, for example, using device data2004 of transaction processing terminal device 110. Connected terminal2102 may also include information for terminal usage 2104, availableterminals 2106 for use by a merchant, and/or unavailable terminals 2108requiring maintenance by terminal harbor device 120. Transactionprocessing terminals 2100 may further include information for in-useterminals 2110, such as health 2112 for in-use terminals 2110, and newterminals 2114 that may be utilized to replace failing terminalsdetermined from health 2112.

Terminal processing application 122 may further receive connectionrequests 2116, such as a request from communication device 130.Communication device 130's request may be associated with specifications2118 for communication device 130, as well as usage information ofcommunication device 130 with previous transaction processing terminaldevices. Based on the aforementioned information a connected device 2122may be determined and connected to communication device 130. Connecteddevice 2122 may be selected based on specifications 2118 and/or usageinformation, and may also be selected based on maintenance schedule2124. For example, maintenance schedule 2124 may be determined when toservice connected terminals 2102 as established in terminal device times2126. Terminal device times 2126 for connected terminals 2102 may bedetermined using a usage schedule 2128 and usages devices 2130, such asdevices requesting connection to connected terminals 2102.

Communication device 130 executes a terminal interface application 140corresponding generally to the specialized hardware and/or softwaremodules and processes described in reference to FIG. 1. In this regard,terminal interface application 140 may be used to connect withtransaction processing terminal device 110 and interface withtransaction processing terminal device 110 to receive transactioninformation from transaction processing terminal device 110. Forexample, terminal interface application 140 includes information forconnected terminals 2200, such as transaction processing terminal device110. Additionally, transaction processing terminal device 110 may beassociated with input mechanisms 2202, such as a scanner, card reader,keypad, or other input device. Using input mechanisms 2202, terminalinterface application 140 may receive input data 2204, such as paymentdata 2206. Additionally, terminal interface application 140 may monitora health 2208 of transaction processing terminal device 110, which maybe reported to terminal harbor device 120, for example, if transactionprocessing terminal device 110 is in danger of failing.

FIG. 4 is an exemplary process flowchart for use of a smart harbordevice for intelligent updating and selection for use of transactionprocessing terminal devices, according to an embodiment. Note that oneor more steps, processes, and methods described herein may be omitted,performed in a different sequence, or combined as desired orappropriate.

At step 402, a status of the transaction processing terminal device isdetermined, wherein the status is associated with operability of thetransaction processing terminal device. The status may be determined bya terminal harbor device or system. In this regard, the terminal harbormay comprise a port structure configured to accept at least onetransaction processing terminal device for management of resources ofthe at least one transaction processing terminal device, a power source,at least one power connector configured to provide power to charge theat least one transaction processing terminal device, a communicationcomponent configured to connect to a plurality of devices, wherein theplurality of devices comprise the at least one transaction processingterminal device and at least one communication device of a user, anon-transitory memory storing a terminal processing application, and oneor more hardware processors configured to execute the terminalprocessing application. The status may be determined when thetransaction processing terminal device is connected to a terminal harbordevice or system.

At step 404, it is determined that the status of the transactionprocessing terminal device requires resolution prior to use of thetransaction processing terminal device. The status may comprises one ofa power level of the transaction processing terminal device, requiredsoftware updates for the transaction processing terminal device,required firmware updates for the transaction processing terminaldevice, and battery maintenance for the transaction processing terminaldevice.

At least one process for resolution of the status of the transactionprocessing terminal device is determined, at step 406. The at least oneprocess may comprise at least one of a preventative maintenance of theat least one transaction processing terminal device, a full lifecycleupdate of the at least one transaction processing terminal device,battery charging for the at least one transaction processing terminaldevice, battery conditioning for the at least one transaction processingterminal device, a software update of the at least one transactionprocessing terminal device, and a firmware update of the at least onetransaction processing terminal device.

At step 408, the at least one process is executed with the transactionprocessing terminal device, wherein executing the at least one processresolves the status. Additionally, it may be determined when to executethe at least one process with the transaction processing terminal devicebased on use of the transaction processing terminal device and the atleast one process may be executed with the transaction processingterminal device during a downtime in use of the transaction processingterminal device. In further embodiments, it may be determined when atleast one other transaction processing terminal device is available,wherein the executing the at least one process with the transactionprocessing terminal device during the downtime in use of the transactionprocessing terminal device is further when the at least one othertransaction processing terminal device is available.

In various embodiments, is may be determined that the transactionprocessing terminal device is ready for use based on the executing theat least one process with the transaction processing terminal device.Additionally, a troubleshooting process with the transaction processingterminal device may be executed, wherein the determining that thetransaction processing terminal device is ready for use after the updateutilizes the troubleshooting process. The information that thetransaction processing terminal device is ready for use may be storedand later used. For example, a request to connect to one of a pluralityof transaction processing terminal devices may be received from acommunication device of a user. Thus, the transaction processingterminal device may be selected based on the information that thetransaction processing terminal device is ready for use, and thetransaction processing terminal device may be connected to thecommunication device based on the information.

In various embodiments, capability information for the communicationdevice may be determined, wherein the connecting the transactionprocessing terminal device to the communication device further uses thecapability information. For example, the capability informationcomprises at least one of software capabilities of the communicationdevice, hardware capabilities of the communication device, a type of thecommunication device, a brand of the communication device, inputcomponents of the communication device, output components of thecommunication device, an operating system of the communication device,graphical user interfaces of the communication device, and communicationmodule components of the communication device.

In further embodiments, wherein selecting the transaction processingterminal device to pair with the communication device further comprisesdetermining that at least one transaction processing terminal device ofthe plurality of payment transaction processing devices is notcompatible with the communication device, or may comprise determiningthat the transaction processing terminal device is compatible with thecommunication device. Additionally, the information for the transactionprocessing terminal device may be stored with terminal information forthe plurality of transaction processing terminal devices, wherein theterminal information comprises identifiers for each of the plurality oftransaction processing terminal devices that establish whether each ofthe plurality of transaction processing terminal devices are ready foruse. Thus, the information may include available and unavailabletransaction processing terminal devices. Thus, where a secondtransaction processing terminal device was not ready for use but wasserviced and now is ready for use, a new identifier for the secondpayment terminal device may be generated, wherein the new identifierestablishes that the second transaction processing terminal device isready for use.

FIG. 5 is a block diagram of a computer system suitable for implementingone or more components in FIG. 1, according to an embodiment. In variousembodiments, the communication device may comprise a personal computingdevice (e.g., smart phone, a computing tablet, a personal computer,laptop, a wearable computing device such as glasses or a watch,Bluetooth device, key FOB, badge, etc.) capable of communicating withthe network. The service provider may utilize a network computing device(e.g., a network server) capable of communicating with the network. Itshould be appreciated that each of the devices utilized by users andservice providers may be implemented as computer system 500 in a manneras follows.

Computer system 500 includes a bus 502 or other communication mechanismfor communicating information data, signals, and information betweenvarious components of computer system 500. Components include aninput/output (I/O) component 504 that processes a user action, such asselecting keys from a keypad/keyboard, selecting one or more buttons,image, or links, and/or moving one or more images, etc., and sends acorresponding signal to bus 502. I/O component 504 may also include anoutput component, such as a display 511 and a cursor control 513 (suchas a keyboard, keypad, mouse, etc.). An optional audio input/outputcomponent 505 may also be included to allow a user to use voice forinputting information by converting audio signals. Audio I/O component505 may allow the user to hear audio. A transceiver or network interface506 transmits and receives signals between computer system 500 and otherdevices, such as another communication device, service device, or aservice provider server via network 170. In one embodiment, thetransmission is wireless, although other transmission mediums andmethods may also be suitable. One or more processors 512, which can be amicro-controller, digital signal processor (DSP), or other processingcomponent, processes these various signals, such as for display oncomputer system 500 or transmission to other devices via a communicationlink 518. Processor(s) 512 may also control transmission of information,such as cookies or IP addresses, to other devices.

Components of computer system 500 also include a system memory component514 (e.g., RAM), a static storage component 516 (e.g., ROM), and/or adisk drive 517. Computer system 500 performs specific operations byprocessor(s) 512 and other components by executing one or more sequencesof instructions contained in system memory component 514. Logic may beencoded in a computer readable medium, which may refer to any mediumthat participates in providing instructions to processor(s) 512 forexecution. Such a medium may take many forms, including but not limitedto, non-volatile media, volatile media, and transmission media. Invarious embodiments, non-volatile media includes optical or magneticdisks, volatile media includes dynamic memory, such as system memorycomponent 514, and transmission media includes coaxial cables, copperwire, and fiber optics, including wires that comprise bus 502. In oneembodiment, the logic is encoded in non-transitory computer readablemedium. In one example, transmission media may take the form of acousticor light waves, such as those generated during radio wave, optical, andinfrared data communications.

Some common forms of computer readable media includes, for example,floppy disk, flexible disk, hard disk, magnetic tape, any other magneticmedium, CD-ROM, any other optical medium, punch cards, paper tape, anyother physical medium with patterns of holes, RAM, PROM, EEPROM,FLASH-EEPROM, any other memory chip or cartridge, or any other mediumfrom which a computer is adapted to read.

In various embodiments of the present disclosure, execution ofinstruction sequences to practice the present disclosure may beperformed by computer system 500. In various other embodiments of thepresent disclosure, a plurality of computer systems 500 coupled bycommunication link 518 to the network (e.g., such as a LAN, WLAN, PTSN,and/or various other wired or wireless networks, includingtelecommunications, mobile, and cellular phone networks) may performinstruction sequences to practice the present disclosure in coordinationwith one another.

Where applicable, various embodiments provided by the present disclosuremay be implemented using hardware, software, or combinations of hardwareand software. Also, where applicable, the various hardware componentsand/or software components set forth herein may be combined intocomposite components comprising software, hardware, and/or both withoutdeparting from the spirit of the present disclosure. Where applicable,the various hardware components and/or software components set forthherein may be separated into sub-components comprising software,hardware, or both without departing from the scope of the presentdisclosure. In addition, where applicable, it is contemplated thatsoftware components may be implemented as hardware components andvice-versa.

Software, in accordance with the present disclosure, such as programcode and/or data, may be stored on one or more computer readablemediums. It is also contemplated that software identified herein may beimplemented using one or more general purpose or specific purposecomputers and/or computer systems, networked and/or otherwise. Whereapplicable, the ordering of various steps described herein may bechanged, combined into composite steps, and/or separated into sub-stepsto provide features described herein.

The foregoing disclosure is not intended to limit the present disclosureto the precise forms or particular fields of use disclosed. As such, itis contemplated that various alternate embodiments and/or modificationsto the present disclosure, whether explicitly described or impliedherein, are possible in light of the disclosure. Having thus describedembodiments of the present disclosure, persons of ordinary skill in theart will recognize that changes may be made in form and detail withoutdeparting from the scope of the present disclosure. Thus, the presentdisclosure is limited only by the claims.

What is claimed is:
 1. A terminal harbor device comprising: a portstructure configured to accept at least one transaction processingterminal device for management of resources of the at least onetransaction processing terminal device; a power source; at least onepower connector configured to provide power to charge the at least onetransaction processing terminal device; a communication componentconfigured to connect to a plurality of devices, wherein the pluralityof devices comprise the at least one transaction processing terminaldevice and at least one communication device of a user; a non-transitorymemory storing a terminal processing application; and one or morehardware processors configured to execute the terminal processingapplication to cause the system to perform operations comprising:receiving device data for the at least one transaction processingterminal device from the communication component, wherein thecommunication component connects to the at least one transactionprocessing terminal device; determining a condition of the at least onetransaction processing terminal device; determining that the conditionrequires resolution prior to use of the at least one transactionprocessing terminal device; and determining at least one process for theresolution of the condition; and executing the at least one process withthe at least one transaction processing terminal device.
 2. The terminalharbor device of claim 1, wherein the communication component connectsto one of the at least one communication device of the user, and whereinthe operations further comprise: determining capabilities of the one ofthe at least one communication device; and selecting one of the at leastone transaction processing terminal device to pair with the one of theat least one communication device based on capabilities; and pairing theone of the at least one transaction processing terminal device with theone of the at least communication device.
 3. The terminal harbor deviceof claim 1, wherein the at least one process comprises at least one of apreventative maintenance of the at least one transaction processingterminal device, a full lifecycle update of the at least one transactionprocessing terminal device, battery charging for the at least onetransaction processing terminal device, battery conditioning for the atleast one transaction processing terminal device, a software update ofthe at least one transaction processing terminal device, and a firmwareupdate of the at least one transaction processing terminal device. 4.The terminal harbor device of claim 3, the at least one payment terminaldevice comprises a plurality of transaction processing terminal devices,and wherein the non-transitory memory further comprises usageinformation for the plurality of transaction processing terminaldevices, and wherein the executing the at least one process with theplurality of transaction processing terminal devices comprises:determining a time for updating or maintenance of each of the pluralityof transaction processing terminal devices using the usage information,wherein the time comprises a downtime in use of the each of theplurality of transaction processing terminal devices; and performingupdates on the each of the plurality of transaction processing terminaldevices based on the time for the updating or the maintenance of theeach of the plurality of transaction processing terminal devices.
 5. Theterminal harbor device of claim 4, wherein the communication componentconnects to at least one of the at least one communication device andthe at least one payment terminal device through short range wirelesscommunications.
 6. A terminal harbor system comprising: a non-transitorymemory; and one or more hardware processors coupled to thenon-transitory memory and configured to read instructions from thenon-transitory memory to cause the communication device system toperform operations comprising: connecting, by the terminal harborsystem, to a first transaction processing terminal device; determining afirst status of the first transaction processing terminal device,wherein the first status is associated with operability of the firsttransaction processing terminal device; determining that the firststatus of the first transaction processing terminal device requiresresolution prior to use of the first transaction processing terminaldevice; determining at least one first process for resolution of thefirst status of the first transaction processing terminal device; andexecuting the at least one first process with the first transactionprocessing terminal device, wherein executing the at least one firstprocess resolves the first status.
 7. The terminal harbor system ofclaim 6, wherein the operations further comprise: determining that thefirst transaction processing terminal device is ready for use based onthe executing the at least one first process with the first transactionprocessing terminal device; and storing information that the firsttransaction processing terminal device is ready for use.
 8. The terminalharbor system of claim 7, wherein the operations further comprise:receiving a request to connect to one of a plurality of transactionprocessing terminal devices from a communication device of a user,wherein the plurality of transaction processing terminal devicescomprise the first transaction processing terminal device; selecting thefirst transaction processing terminal device based on the informationthat the first transaction processing terminal device is ready for use;and connecting the first transaction processing terminal device to thecommunication device based on the information.
 9. The terminal harborsystem of claim 8, wherein the information is stored with terminalinformation for the plurality of transaction processing terminaldevices, and wherein the terminal information comprises identifiers foreach of the plurality of transaction processing terminal devices thatestablish whether the each of the plurality of transaction processingterminal devices is ready for use.
 10. The terminal harbor system ofclaim 9, wherein the operations further comprise: determining a secondstatus of a second transaction processing terminal device of theplurality of transaction processing terminal devices from the terminalinformation, wherein the second status is associated with operability ofthe second transaction processing terminal device; determining that thesecond status of the second transaction processing terminal devicerequires resolution prior to use of the second transaction processingterminal device; determining at least one second process for resolutionof the second status of the second transaction processing terminaldevice; and executing the at least one second process with the secondtransaction processing terminal device, wherein executing the at leastone second process resolves the second status; determining that thesecond transaction processing terminal device is ready for use; andestablishing a new identifier for the second status in the terminalinformation, wherein the new identifier establishes that the secondtransaction processing terminal device is ready for use.
 11. Theterminal harbor system of claim 8, wherein the operations furthercomprise: determining capability information for the communicationdevice, wherein the connecting the first transaction processing terminaldevice to the communication device further uses the capabilityinformation.
 12. The terminal harbor system of claim 11, wherein thecapability information comprises at least one of software capabilitiesof the communication device, hardware capabilities of the communicationdevice, a type of the communication device, a brand of the communicationdevice, input components of the communication device, output componentsof the communication device, an operating system of the communicationdevice, graphical user interfaces of the communication device, andcommunication module components of the communication device.
 13. Theterminal harbor system of claim 11, wherein the selecting the firsttransaction processing terminal device further comprises determiningthat at least one second transaction processing terminal device of theplurality of transaction processing terminal devices is not compatiblewith the communication device using the capability information.
 14. Theterminal harbor system of claim 6, wherein the first status comprisesone of a power level of the first transaction processing terminaldevice, software updates for the first transaction processing terminaldevice, firmware updates for the first transaction processing terminaldevice, battery maintenance for the first transaction processingterminal device, and cache availability for a cache of storedtransactions.
 15. The terminal harbor system of claim 6, wherein theexecuting the at least one first process with the first transactionprocessing terminal device comprises: determining when to execute the atleast one first process with the first transaction processing terminaldevice based on use of the first transaction processing terminal device;and executing the at least one first process with the first transactionprocessing terminal device during a downtime in use of the firsttransaction processing terminal device.
 16. The terminal harbor systemof claim 15, wherein the executing the at least one first process withthe first transaction processing terminal device further comprises:determining when at least one other transaction processing terminaldevice is available, wherein the executing the at least one firstprocess with the first transaction processing terminal device during thedowntime in use of the first transaction processing terminal device isfurther when the at least one other transaction processing terminaldevice is available.
 17. A method comprising: connecting, by theterminal harbor system, to at least one transaction processing terminaldevice; detecting that the transaction processing terminal device has asoftware update available for use with the transaction processingterminal device; retrieving the software update from a service providerassociated with the transaction processing terminal device; updating thetransaction processing terminal device with the software update; anddetermining that the transaction processing terminal device is ready foruse after the software update.
 18. The method of claim 17, furthercomprising: executing a troubleshooting process with the transactionprocessing terminal device, wherein the troubleshooting processdetermines whether the transaction processing terminal device is readyfor use after the software update, and wherein the determining that thetransaction processing terminal device is ready for use after thesoftware update uses the troubleshooting process; and storinginformation that the transaction processing terminal device is ready foruse after the software update.
 19. The method of claim 18, furthercomprising: receiving a request to use the transaction processingterminal device from a communication device; determining that thetransaction processing terminal device is available for use using theinformation; and in response to the request, connecting the transactionprocessing terminal device for use with the communication device. 20.The method of claim 18, wherein the information further comprisesavailable and unavailable transaction processing terminal devices foruse by a user with a communication device.